Report request steps

Step #1

Using a web browser, a user connects to your web server and makes a request. The web browser uses a Report Viewer to communicate with the server.

Step #2

If you are using a Microsoft or Netscape web server, the request is processed using ISAP or NSAPI. If you are using a Lotus Domino Server or another CGI compliant server, the request is processed using CGI. The request is then forwarded to the Web Component Server.

Step #3

After the Web Component Server has queued and determined the type of request, it is forwarded to the Page Server.

The only exception is the processing of an HTML request. The images in an HTML report do not follow the next two steps, they automatically go to step 4.

Step #3.1 and #3.2

The Page Server takes care of EPF generation and caching. When it is finished, the EPF details are forwarded to the Web Component Server.

Step #4

If this is an HTML request, the Web Component Server translates the report page to HTML. The Web Component Server then forwards the HTML and stores the .CRI files until they are requested.

Step #5

The web server forwards the report to the appropriate Report Viewer which displays the report in the user's browser.



Seagate Software, Inc.
http://www.seagatesoftware.com
Please send comments to:
techpubs@seagatesoftware.com